-
Notifications
You must be signed in to change notification settings - Fork 339
feat: Support Qv2 CLI social login #3060
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: qv2
Are you sure you want to change the base?
Conversation
| IdentityFuture::new_boxed(Box::pin(async { | ||
| let database = Database::new().await?; | ||
|
|
||
| if let Ok(Some(token)) = builder_id::BuilderIdToken::load(&database).await { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need to check both all times?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The UnifiedBearerResolver needs to support two login paths — Builder ID and Social.
A user may complete login through either method. Therefore, during the resolution phase, we need attempt both methods
* feat: New continuation id logic * chore: Centralize metadata * chore: Moves struct to right place --------- Co-authored-by: Kenneth S. <[email protected]>
83daff1 to
de21929
Compare
Issue #, if available:
Description of changes:
Integrates with unified authentication portal supporting Google, GitHub, BuilderID, AWS IdC, and Internal auth methods.
Local environments: Browser-based OAuth flow via unified portal
Remote environments: Existing device flow (BuilderID/IdC(Internal))
User Experience
Local:
q login
Remote:
q login (--use-decivce-code)existing auth flow, prompted user that social login is not supported here
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.